Signaling for downlink coordinated multipoint in a wireless communication system

ABSTRACT

Embodiments herein describe apparatuses, systems, and methods for signaling to support downlink coordinated multipoint (CoMP) communications with a user equipment (UE) in a wireless communication network. In embodiments, the UE may be configured with a plurality of channel state information (CSI) processes (e.g., via radio resource control (RRC) signaling) to use for providing CSI feedback to an evolved Node B (eNB) to support downlink CoMP communications. The UE may be configured with a plurality of sets of CSI processes. The UE may further receive a downlink control information (DCI) message from the eNB that indicates one of the configured sets of CSI processes on which the UE is to provide CSI feedback to the UE. The UE may generate the CSI feedback for the indicated set of CSI processes, and transmit the CSI feedback to the eNB in a CSI report.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 13/730,289, filed Dec. 28, 2012, entitled “SIGNALING FORDOWNLINK COORDINATED MULTIPOINT IN A WIRELESS COMMUNICATION SYSTEM,”which claims priority to U.S. Provisional Patent Application No.61/646,223, filed May 11, 2012, entitled “ADVANCED WIRELESSCOMMUNICATION SYSTEMS AND TECHNIQUES,” the entire disclosure of which ishereby incorporated by reference.

FIELD

Embodiments of the present invention relate generally to the field ofcommunications, and more particularly, to signaling for downlinkcoordinated multipoint communications in a wireless communicationsystem.

BACKGROUND

Coordinated multipoint (CoMP) systems have been developed in order toimprove various operational parameters in wireless networks. There arethree types of CoMP systems: joint transmission (JT); dynamic pointselection (DPS); and cooperative scheduling and cooperative beamforming(CS/CB). In JT CoMP, both a serving point, e.g., an enhanced node basestation (eNB), and a coordinating point, e.g., another eNB, may send thesame data to a user equipment (UE). In DPS CoMP, a transmission pointmay be dynamically selected among different candidates, e.g., amacro-node eNB and a pico-node eNB. In CS/CB CoMP, coordinating nodesmay suppress interference of interfering channels. However, the eNB maynot have sufficient control and signaling mechanisms for effectivemanagement of CoMP communications with a UE.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will be readily understood by the following detaileddescription in conjunction with the accompanying drawings. To facilitatethis description, like reference numerals designate like structuralelements. Embodiments are illustrated by way of example and not by wayof limitation in the figures of the accompanying drawings.

FIG. 1 schematically illustrates a wireless communication networkincluding a user equipment (UE) and a plurality of evolved Node Bs(eNBs) in accordance with various embodiments.

FIG. 2 is a table that maps values of a channel state information (CSI)request field to trigger aperiodic CSI feedback in accordance withvarious embodiments.

FIG. 3 is a table that maps values of another CSI request field inaccordance with various embodiments.

FIG. 4 illustrates a bitmap that may be used to indicate one or more CSIprocesses that are included in a set of CSI processes for triggeringaperiodic CSI feedback in accordance with various embodiments.

FIG. 5 is a flowchart illustrating a method for triggering aperiodic CSIfeedback that may be performed by a UE in accordance with variousembodiments.

FIG. 6 is a table that maps values of a cell-specific reference signal(CRS) configuration parameter to corresponding values for a number ofCRS antenna ports and a CRS frequency shift in accordance with variousembodiments.

FIG. 7 schematically depicts an example system in accordance withvarious embodiments.

DETAILED DESCRIPTION

Illustrative embodiments of the present disclosure include, but are notlimited to, methods, systems, computer-readable media, and apparatusesfor signaling to support downlink coordinated multipoint communicationsin a wireless communication network.

Various aspects of the illustrative embodiments will be described usingterms commonly employed by those skilled in the art to convey thesubstance of their work to others skilled in the art. However, it willbe apparent to those skilled in the art that alternate embodiments maybe practiced with only some of the described aspects. For purposes ofexplanation, specific numbers, materials, and configurations are setforth in order to provide a thorough understanding of the illustrativeembodiments. However, it will be apparent to one skilled in the art thatalternate embodiments may be practiced without the specific details. Inother instances, well-known features are omitted or simplified in ordernot to obscure the illustrative embodiments.

Further, various operations will be described as multiple discreteoperations, in turn, in a manner that is most helpful in understandingthe illustrative embodiments; however, the order of description shouldnot be construed as to imply that these operations are necessarily orderdependent. In particular, these operations need not be performed in theorder of presentation.

The phrase “in some embodiments” is used repeatedly. The phrasegenerally does not refer to the same embodiments; however, it may. Theterms “comprising,” “having,” and “including” are synonymous, unless thecontext dictates otherwise. The phrase “A and/or B” means (A), (B), or(A and B). The phrase “A/B” means (A), (B), or (A and B), similar to thephrase “A and/or B”. The phrase “at least one of A, B and C” means (A),(B), (C), (A and B), (A and C), (B and C) or (A, B and C). The phrase“(A) B” means (B) or (A and B), that is, A is optional.

Although specific embodiments have been illustrated and describedherein, it will be appreciated by those of ordinary skill in the artthat a wide variety of alternate and/or equivalent implementations maybe substituted for the specific embodiments shown and described, withoutdeparting from the scope of the embodiments of the present disclosure.This application is intended to cover any adaptations or variations ofthe embodiments discussed herein. Therefore, it is manifestly intendedthat the embodiments of the present disclosure be limited only by theclaims and the equivalents thereof

As used herein, the term “module” may refer to, be part of, or includean Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group) and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablecomponents that provide the described functionality.

FIG. 1 schematically illustrates a wireless communication network 100 inaccordance with various embodiments. Wireless communication network 100(hereinafter “network 100”) may be an access network of a 3rd GenerationPartnership Project (3GPP) long-term evolution (LTE) network such asevolved universal terrestrial radio access network (E-UTRAN). Thenetwork 100 may include a base station, e.g., enhanced node base station(eNB) 104, configured to wirelessly communicate with user equipment (UE)108.

At least initially, the eNB 104 may have an established wirelessconnection with the UE 108 and may operate as a serving node within aCoMP measurement set. One or more additional eNBs of the network 100,e.g., eNBs 112 and 116, may also be included within the CoMP measurementset. eNBs 112 and 116 may be configured to facilitate wirelesscommunication with the UE 108 through coordination with the eNB 104. Theone or more additional eNBs may be collectively referred to as“coordinating nodes.” An eNB may transition between coordinating andserving node roles.

The serving node and coordinating nodes may communicate with one anotherover a wireless connection and/or a wired connection (e.g., a high-speedfiber backhaul connection).

The eNBs may each have generally the same transmission powercapabilities as one another or, alternatively, some of the eNBs may haverelatively lower transmission power capabilities. For example, in oneembodiment the eNB 104 may be a relatively high-power base station suchas a macro eNB, while the eNBs 112 and 116 may be relatively low-powerbase stations, e.g., pico eNBs and/or femto eNBs.

The eNB 104 may be configured to communicate with the UE 108 over one ormore component carriers. Each component carrier may be associated with afrequency band used for communications on the component carrier.Individual component carriers may be considered separate cells in someembodiments. In some embodiments, the eNB 104 may communicate with theUE 108 over a plurality of the component carriers (of differentfrequencies) using carrier aggregation. The UE 108 may receive controlinformation on a primary serving cell, and may receive other informationon secondary serving cells. The primary and secondary serving cells maybe associated with respective component carriers. Carrier aggregationmay be used in addition to, or instead of, CoMP communications.

The UE 108 may include a communications module 120 and a feedback module124 coupled with one another. The UE 108 may further include a CoMPmodule 128 coupled with the communications module 120 and/or feedbackmodule 124. The communications module 120 may be further coupled withone or more of a plurality of antennas 132 of the UE 108 forcommunicating wirelessly over network 100.

The UE 108 may include any suitable number of antennas. In variousembodiments, the UE 108 may include at least as many antennas as anumber of simultaneous spatial layers or streams received by the UE 108from the eNBs, although the scope of the present disclosure may not belimited in this respect. The number of simultaneous spatial layers orstreams may also be referred to as transmission rank, or simply rank.

One or more of the antennas 132 may be alternately used as transmit orreceive antennas. Alternatively, or additionally, one or more of theantennas 132 may be dedicated receive antennas or dedicated transmitantennas.

eNB 104 may include a communications module 136, a CoMP managementmodule 140, and an aperiodic feedback module 144 coupled with oneanother at least as shown. The communications module 136 may be furthercoupled with one or more of a plurality of antennas 152 of the eNB 104.The communications module 136 may communicate (e.g., transmit and/orreceive) with one or more UEs (e.g., UE 108). In various embodiments,the eNB 104 may include at least as many antennas as a number ofsimultaneous transmission streams transmitted to the UE 108, althoughthe scope of the present disclosure may not be limited in this respect.One or more of the antennas 152 may be alternately used as transmit orreceive antennas. Alternatively, or additionally, one or more of theantennas 152 may be dedicated receive antennas or dedicated transmitantennas.

In various embodiments, the UE 108 may be configured with one or moreCSI processes for an individual cell (e.g., component carrier). A CSIprocess may include an associated CSI-reference signal (CSI-RS) resourceand/or an associated CSI-interference measurement (CSI-IM) resource. Insome embodiments, the CSI-RS resource may be a non-zero power (NZP)CSI-RS resource. The UE 108 may further receive a cell index and/or aCSI process identifier (ID) (e.g., within a given cell) associated witheach configured CSI process. The one or more CSI processes may beconfigured for the UE 108 (e.g., by the eNB 104) using higher layersignaling, such as via radio resource control (RRC) signaling. The CSIprocesses may be used for the UE 108 to generate CSI feedback for theeNB 104 to facilitate downlink CoMP communication with the UE 108.

In various embodiments, the feedback module 124 of the UE 108 mayreceive, via the communications module 120, a downlink controlinformation (DCI) message from the eNB 104. The DCI message may bereceived, for example, on a physical downlink control channel (PDCCH).The PDCCH may in some embodiments be an enhanced PDCCH (EPDCCH) or othertype of PDCCH. The DCI message may include a CSI request field toindicate one or more CSI processes for which the UE 108 is to provideCSI feedback to the eNB 104. Accordingly, the DCI message may facilitateaperiodic reporting of CSI feedback by the UE 108. In some embodiments,the CSI request field may be two bits to indicate one of four possiblevalues. Other embodiments of the CSI request field may include otherquantities of bits.

The feedback module 124 may generate the CSI feedback for the indicatedCSI processes. The CSI feedback may include, for example, a channelquality indicator (CQI), a precoding matrix indicator (PMI), one or moreselected subbands, and/or a rank indicator (RI) for the CSI process. Thefeedback module 124 may then transmit, via the communications module120, a CSI report to the eNB 104 that includes the generated CSIfeedback. The CSI report may be transmitted, for example, on a physicaluplink shared channel (PUSCH).

FIG. 2 illustrates a table 200 that maps values of a two-bit CSI requestfield in accordance with some embodiments. As shown in table 200, theCSI request field may have a value ‘01’ to indicate that the feedbackmodule 124 is to provide a CSI report for a first set of CSI processesconfigured for a serving cell of the UE 108. The serving cell may be aprimary serving cell on which the UE 108 receives the DCI that includesthe CSI request field. In some embodiments, the UE 108 may identify theserving cell for which the UE 108 is to provide the CSI feedback basedon the component carrier on which the UE 108 receives the DCI.

In some embodiments, the value ‘01’ may indicate that the UE 108 is toprovide the CSI feedback for all of the CSI processes associated withthe serving cell (e.g., the first set of CSI processes may include allthe CSI processes associated with the serving cell). In otherembodiments, the first set of CSI processes may include a subset (e.g.,less than all) of the CSI processes associated with the serving cell.For example, the first set of CSI processes may be configured for the UE108 via higher layers (e.g., via RRC signaling).

In various embodiments, the CSI request field may have a value a value‘10’ to indicate that that the feedback module 124 is to provide a CSIreport for a second set of CSI processes. Alternatively, the CSI requestfield may have a value ‘11’ to indicate that the feedback module 124 isto provide a CSI report for a third set of CSI processes. The second setand/or third set of CSI processes may be configured by higher layers(e.g., RRC signaling), for example by the eNB 104, to indicate the CSIprocesses that are included in the second and/or third sets.

The CSI report for the first set, second set and/or third set may beused by the eNB 104 to manage downlink CoMP communications with the UE108. In some embodiments, the CSI report for the first set, second setand/or third set may be used by the eNB 104 to manage carrieraggregation communications with the UE 108 in addition to CoMPcommunications. The CSI request field may be similar to a CSI requestfield used to trigger CSI reports to support carrier aggregationcommunications. However, the CSI request field for carrier aggregationmay only trigger CSI reports for one CSI process of a specific cell orset of cells, and may not allow triggering of CSI reports for more thanone CSI process associated with a given cell and/or associated withdifferent cells. Furthermore, the second and/or third sets of CSIprocesses may include CSI processes on different cells of the samefrequency (e.g., cells of the same frequency that are transmitted bydifferent eNBs).

In some embodiments, the CSI request field as described herein may beused when the UE 108 is configured in transmission mode 10, as definedin LTE Advanced Release 11. Transmission mode 10 may support CoMPcommunications with the UE. In transmission mode 10, the UE 108 mayprovide CSI feedback for one or more CSI processes as described herein.The UE 108 may receive scheduling information using DCI format 2D. Insome embodiments, DCI format 1A may be used as a fall-back mode. The UE108 may also receive PDSCH mapping parameters for other cells besidesthe serving cell. Additionally, or alternatively, the UE 108 may useUE-specific reference signals for demodulation of the PDSCH.

The second set and/or third set of CSI processes may include any numberof one or more CSI processes. In some embodiments, the second set and/orthird set may include a plurality of CSI processes. The second set andthird set may include one or more common CSI processes in someembodiments (e.g., one or more CSI processes that are included in boththe second set and the third set). In other embodiments, the second setand third set may each include only one CSI process. The CSI processesof the second set and/or third set may include one or more CSI processesthat are associated with a different cell from the serving cell.Additionally, or alternatively, the second set and/or third set mayinclude a plurality of CSI processes associated with different cells.

In various embodiments, the CSI request field may include a value ‘00’to indicate that no aperiodic CSI report is triggered by the DCImessage. The value ‘00’ may be used, for example, when a DCI message istransmitted to the UE 108 for another purpose besides to triggeraperiodic CSI reporting.

Although specific values for the two-bit CSI request field are shown intable 200, it will be apparent that the values may be mapped tocorresponding actions in any suitable manner, which may differ from thatshown in table 200. For example, in another embodiment, the value ‘00’may trigger CSI reporting for the first set of CSI processes.

As described herein, the CSI request field may be used by the eNB 104 totrigger CSI reports for a set of CSI processes. The eNB 104 maydynamically change the set of CSI processes for which the eNB 104requests CSI feedback from the UE 104. The aperiodic feedback module 144of the eNB 104 may receive the CSI reports and the CoMP managementmodule 140 may use the CSI feedback information included in the CSIreports to manage downlink CoMP communications with the UE.

In other embodiments, the CSI request field may include only one bit.The bit may have a first value (e.g., ‘1’) to trigger a CSI report forall CSI processes of the serving cell. The bit may have a second value(e.g., ‘0’) if no CSI report is triggered by the DCI message. Theone-bit CSI request field may be used, for example, when the UE 108 isusing a transmission mode with a common search space for PDCCH decoding(as opposed to a UE-specific search space).

FIG. 3 illustrates a table 300 that maps values of a two-bit CSI requestfield in accordance with another embodiment. As shown in FIG. 3, thetwo-bit CSI request field may include a value ‘01’ to indicate that theUE 108 is to provide a CSI report for a first set of CSI processes, or avalue ‘10’ to indicate that the UE 108 is to provide a CSI report for asecond set of CSI processes. The CSI request field may further include avalue ‘11’ to indicate that the UE 108 is to provide a CSI report forboth the first set and second set of CSI processes. The CSI requestfield may include a value ‘00’ to indicate that no aperiodic CSI reportis triggered by the DCI message.

It will be apparent that other suitable configurations of the CSIrequest field, besides the configurations shown in FIGS. 2 and 3, may beused for triggering aperiodic CSI reports for different sets of CSIprocesses. For example, in another embodiment, the CSI request field maybe similar to that shown in table 300, but with the value ‘00’ toindicate that the UE 108 is to provide a CSI report for a set of CSIprocesses configured for the serving cell.

In various embodiments, the sets of CSI processes that may be triggeredfor CSI reporting by the CSI request field (e.g., the first, second,and/or third sets described above) may be configured by the eNB 104using respective bitmaps. The bitmaps may be transmitted to the UE 108by the eNB 104 (e.g., via RRC signaling) to indicate which CSI processesare included in a given set of CSI processes. For example, FIG. 4illustrates a bitmap 400 in accordance with various embodiments. Bitmap400 includes a plurality of bits (e.g., bits b₀, b₁, . . . b_(NK-1)),and individual bits may correspond to individual CSI processes toindicate if the CSI process is included in the set of CSI processesdefined by the bitmap 400. The bits may be ordered in the bitmap 400according to the cell index (e.g., in increasing order of cell index),and bits corresponding to CSI processes associated with the same cellindex may be ordered by their respective CSI IDs. For example, bitmap400 includes bits corresponding to K+1 component carriers (e.g., withcell index 0 to cell index K). Each component carrier may include amaximum of N configured CSI processes. The groups of bits correspondingto CSI processes having the same cell index are arranged in the bitmap400 in increasing order of cell index (e.g., with the bits correspondingto the CSI processes of cell index 0 (b₀-b_(N-1)) disposed in the bitmap400 before the bits corresponding to the CSI processes of cell index 1(b_(N)-b_(2N-1))). Within the groups of bits corresponding to CSIprocesses with the same cell index, the bits are ordered in increasingorder of CSI process ID. For example, bit b₀ corresponds to the CSIprocess with cell index 0 and CSI process ID 0, and bit b₁ correspondsto the CSI process with cell index 0 and CSI process ID 1, etc.

As discussed above, the eNB 104 may transmit a plurality of bitmapssimilar to bitmap 400 to define different sets of CSI processes foraperiodic CSI reporting. The aperiodic CSI reporting for an individualset may then be triggered by a DCI message including a CSI request fieldas described herein. In some embodiments, the bitmaps to define the setsof CSI processes for aperiodic CSI reporting may be transmitted as partof the CSI process configuration process (e.g., upon the UE 108 becomingRRC connected with the eNB 104). For example, the CoMP management module140 of the eNB 104 may transmit the bitmaps contemporaneously with theCSI process configuration information (e.g., the CSI-RS resource and/orCSI-IM resource) for the individual CSI processes. Additionally, oralternatively, the bitmaps may be transmitted separately from the CSIprocess configuration information to define and/or modify the sets ofCSI processes for aperiodic CSI reporting.

In some embodiments, the CoMP management module 140 of the eNB 104 mayfurther transmit a codebookSubsetRestriction parameter associated withindividual CSI processes. The codebookSubsetRestriction parameter may betransmitted as part of the configuration of the CSI processes. ThecodebookSubsetRestriction parameter may indicate a subset of PMIs withina codebook to be used by the UE 104 for CSI reporting for the respectiveCSI process. Alternatively, or additionally, thecodebookSubsetRestriction parameter may be configured for each NZPCSI-RS resource and/or subset of subframes.

In some embodiments, the eNB 104 may configure one or more CSIdependencies between a plurality of configured CSI processes. Forexample, the eNB 104 may indicate for the UE 108 to report CSI feedbackfor a plurality of CSI processes on the same rank and/or over the samepreferred sub-bands.

As discussed above, the feedback module 124 of the UE 108 may generateCSI feedback for one or more CSI processes triggered by the CSI requestfield. The CSI feedback may be generated based on the CSI-RS resourceand/or CSI-IM resource configured for the CSI process. The CSI feedbackmay include, for example, a CQI, a PMI, one or more selected subbands,and/or an RI for the CSI process. The UE 108 may transmit the CSIfeedback to the eNB 104 in a CSI report.

In some embodiments, the CSI feedback for a plurality of CSI processesmay be concatenated in a same CSI report. For example, the CSI feedbackfor multiple CSI processes may be concatenated according to the CSIprocess index and/or cell index of the CSI process. In one embodiment,the CSI feedback for groups of CSI processes associated with a samecomponent carrier (e.g., having the same cell index) may be ordered inthe CSI report in increasing order of cell index. The CSI feedback maybe arranged within the individual groups in increasing order of the CSIprocess indexes of the individual CSI processes having the same cellindex.

In some cases, one or more components of the CSI feedback for a firstCSI process may be the same as one or more components of the CSIfeedback for the second CSI process. For example, the RI reported forthe first and second CSI processes may be the same. In some embodiments,the shared component (e.g., the RI in this example) may be omitted fromthe CSI report for the first CSI process or the second CSI process. Thismay reduce the bandwidth required for the CSI report.

In some embodiments, the CSI report may be encoded using turbo codingand/or cyclic redundancy check (CRC) encoding. For example, turbo codingand/or CRC encoding may be used to encode the CQI and PMI reports. Thismay facilitate having a CSI report with a large payload size.

FIG. 5 is a flowchart illustrating a method 500 for triggering aperiodicCSI feedback in accordance with various embodiments. Method 500 may beperformed by a UE, such as UE 108. In some embodiments, the UE mayinclude and/or have access to one or more computer-readable media havinginstructions stored thereon, that, when executed, cause the UE toperform the method 500. Additionally, or alternatively, in someembodiments, the UE may include circuitry to perform the method 500.

At 504, the UE may receive a first bitmap (e.g., bitmap 400) from an eNB(e.g., eNB 104) over a wireless communication network (e.g., network100). The first bitmap may indicate one or more CSI processes that areincluded in a first set of CSI processes. For example, the first bitmapmay include a plurality of bits, and individual bits may correspond toindividual CSI processes to indicate if the CSI process is included inthe first set of CSI processes. Individual bits may have a first value(e.g., ‘1’) to indicate that the corresponding CSI process is includedin the first set, or a second value (e.g., ‘0’) to indicate that thecorresponding CSI process is not included in the first set. In someembodiments, the plurality of bits may be ordered in the bitmapaccording to a cell index of the CSI process (e.g., in increasing orderof cell index), and the bits corresponding to CSI processes with thesame cell index may be ordered by a CSI process ID of the CSI process(e.g., in increasing order of CSI process ID).

At 508, the UE may receive a second bitmap from the eNB. The secondbitmap may indicate one or more CSI processes that are included in asecond set of CSI processes. The second bitmap may have a similararrangement of bits to that described above for the first bitmap, butwith different bits being set to the first value (e.g., ‘1’). In someembodiments, the first and second sets may include one or more CSIprocesses in common.

At 512, the UE may receive a DCI message from the eNB. The DCI messagemay include a CSI request field to request CSI feedback to supportdownlink CoMP transmission to the UE. In some embodiments, the CSIrequest field may include two bits to form one of four values. The CSIrequest field may have a first value to indicate that the UE is toprovide CSI feedback for the first set of CSI processes (e.g.,configured at 504), or a second value to indicate that the UE is toprovide CSI feedback for the second set of CSI processes (e.g.,configured at 508).

At 516, the UE may generate CSI feedback for the CSI processes indicatedby the CSI request field.

At 520, the UE may transmit the generated CSI feedback to the eNB. TheCSI feedback may be included in one or more CSI reports.

In some embodiments, the CSI request field may have a third value toindicate that the UE is to provide CSI feedback for a set of CSIprocesses configured for a serving cell of the UE. The serving cell maybe identified by the component carrier on which the eNB transmits theDCI to the UE that includes the CSI request field. The set of CSIprocesses configured for the serving cell may include all the CSIprocesses configured for the serving cell or a subset of all the CSIprocesses configured for the serving cell.

In some embodiments, the CSI request field may have a fourth value toindicate that no CSI report is triggered by the DCI message.

In other embodiments, the third or fourth value of the CSI request fieldmay be used to indicate that the UE is to provide CSI feedback for boththe first set and second set of CSI processes (e.g., as configured at504 and 508, respectively).

In various embodiments, the UE 108 may receive information related to aresource element mapping configuration of a physical downlink sharedchannel (PDSCH) for the UE 108 to use to receive the PDSCH. In someembodiments, the CoMP module 128 of the UE 108 may receive an RRCmessage from the eNB 104 that includes PDSCH resource element mappingparameters for a plurality of PDSCH mapping configurations. The PDSCHresource element mapping parameters may include, for example, a numberof cell-specific reference signal (CRS) antenna ports, a CRS antennaport shift, a PDSCH starting symbol, a multicast-broadcast singlefrequency network subframe configuration for the individual PDSCHmapping configurations. In some embodiments, the PDSCH resource elementmapping parameters may further include a non-zero power CSI-RSidentifier and/or a CSI process identifier associated with the PDSCHmapping configuration. The PDSCH mapping configurations may be furtherassociated with (either explicitly or implicitly) a PDSCH mappingconfiguration ID.

Any suitable number of PDSCH mapping configurations may be configuredfor the UE 108. For example, in one embodiment, four PDSCH mappingconfigurations may be configured for the UE 108. In some embodiments,the PDSCH mapping configurations may be generic (e.g., not associatedwith specific cells). In other embodiments, the PDSCH mappingconfigurations may be associated with respective individual cells.

In some embodiments, the number of CRS antenna ports and the CRS antennaport shift may be jointly encoded into a CRS configuration parameter.For example, FIG. 6 illustrates a table 600 that shows the mapping of avalue of the CRS configuration parameter to corresponding values for thenumber of CRS antenna ports and the CRS antenna port shift. As shown intable 600, a first value (e.g., value 0) of the CRS configurationparameter may indicate that the PDSCH mapping configuration has 4antenna ports and a CRS frequency shift of 2 subframes. In someembodiments, a PDSCH mapping configuration may have a number of antennaports of 1, 2, or 4. A PDSCH mapping configuration with 1 antenna portmay have one of six CRS frequency shifts (e.g., 0, 1, 2, 3, 4, or 5subframes), while a PDSCH mapping configuration with 2 or 4 antennaports may have one of three CRS frequency shifts (e.g., 0, 1, or 2subframes). Accordingly, jointly encoding the number of CRS antennaports and the CRS antenna port shift may require one fewer bit thanencoding them separately.

In various embodiments, the UE 108 may receive a DCI message from theeNB 104 indicating one of the PDSCH mapping configurations (e.g., afirst PDSCH mapping configuration) of the plurality of PDSCH mappingconfigurations for the UE 108 to use to receive the PDSCH. For example,the DCI message may include the PDSCH mapping configuration IDcorresponding to one of the PDSCH mapping configurations that wereconfigured using RRC signaling as described above. In some embodiments,the PDSCH mapping configuration ID may be jointly encoded with acomponent carrier indicator that indicates a first component carrier, ofa plurality of configured component carriers, on which the PDSCH is tobe transmitted to the UE 108. For example, the DCI message may include acarrier aggregation cell identification field (CIF) that indicates thePDSCH mapping configuration and the component carrier for the UE to useto receive the PDSCH. In some embodiments, the CIF may be three bits.The three-bit CIF may have eight different values to indicate one of twocomponent carriers and one of four PDSCH mapping configurations. Inother embodiments, the PDSCH mapping configuration ID may be included ina separate field from the CIF.

The UE 108 may use the PDSCH resource element mapping parameters toreceive the PDSCH via CoMP communication. For example, the PDSCHresource element mapping parameters may facilitate the avoidance of CRSto PDSCH collision. For joint transmission (JT) CoMP, the UE 108 may usethe mapping parameters to determine the instantaneous rate matchingpattern when resource element muting is used to mitigate CRS to PDSCHcollision. For dynamic point selection (DPS), the mapping parameters maybe used to avoid the need for resource element muting. Additionally, forDPS in transmission modes 1, 2, 3 and 4, as proposed in the LTE-AdvancedStandard Release 11, the UE 108 may use the PDSCH resource elementmapping parameters to determine the specific CRS that should be used fordemodulation of the PDSCH.

In embodiments in which the PDSCH mapping configurations are associatedwith respective individual cells (component carriers), the transmittingcell may be indicated to the UE 108 to indicate the PDSCH mappingconfiguration for the UE to use to receive the PDSCH. In someembodiments, the carrier aggregation CIF may be used to indicate thetransmitting cell for downlink CoMP (e.g., using values of the CIF thatare not used for carrier aggregation). It will be apparent that otherbit-sizes and/or arrangements may be used to indicate the PDSCH mappingconfiguration for the UE 108 to use.

The eNB 104/112/116 and/or UE 108 described herein may be implementedinto a system using any suitable hardware and/or software to configureas desired. FIG. 7 illustrates, for one embodiment, an example system700 comprising one or more processor(s) 704, system control logic 708coupled with at least one of the processor(s) 704, system memory 712coupled with system control logic 708, non-volatile memory (NVM)/storage716 coupled with system control logic 708, a network interface 720coupled with system control logic 708, and input/output (I/O) devices732 coupled with system control logic 708.

The processor(s) 704 may include one or more single-core or multi-coreprocessors. The processor(s) 704 may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, baseband processors, etc.).

System control logic 708 for one embodiment may include any suitableinterface controllers to provide for any suitable interface to at leastone of the processor(s) 704 and/or to any suitable device or componentin communication with system control logic 708.

System control logic 708 for one embodiment may include one or morememory controller(s) to provide an interface to system memory 712.System memory 712 may be used to load and store data and/orinstructions, for example, for system 700. System memory 712 for oneembodiment may include any suitable volatile memory, such as suitabledynamic random access memory (DRAM), for example.

NVM/storage 716 may include one or more tangible, non-transitorycomputer-readable media used to store data and/or instructions, forexample. NVM/storage 716 may include any suitable non-volatile memory,such as flash memory, for example, and/or may include any suitablenon-volatile storage device(s), such as one or more hard disk drive(s)(HDD(s)), one or more compact disk (CD) drive(s), and/or one or moredigital versatile disk (DVD) drive(s), for example.

The NVM/storage 716 may include a storage resource physically part of adevice on which the system 700 is installed or it may be accessible by,but not necessarily a part of, the device. For example, the NVM/storage716 may be accessed over a network via the network interface 720 and/orover Input/Output (I/O) devices 732.

Network interface 720 may have a transceiver 722 to provide a radiointerface for system 700 to communicate over one or more network(s)and/or with any other suitable device. The transceiver 722 may implementcommunications module 120 of UE 108 or communications module 136 of eNB104. In various embodiments, the transceiver 722 may be integrated withother components of system 700. For example, the transceiver 722 mayinclude a processor of the processor(s) 704, memory of the system memory712, and NVM/Storage of NVM/Storage 716. Network interface 720 mayinclude any suitable hardware and/or firmware. Network interface 720 mayinclude a plurality of antennas to provide a multiple input, multipleoutput radio interface. Network interface 720 for one embodiment mayinclude, for example, a wired network adapter (e.g., an Ethernet networkadapter), a wireless network adapter, a telephone modem, and/or awireless modem.

For one embodiment, at least one of the processor(s) 704 may be packagedtogether with logic for one or more controller(s) of system controllogic 708. For one embodiment, at least one of the processor(s) 704 maybe packaged together with logic for one or more controllers of systemcontrol logic 708 to form a System in Package (SiP). For one embodiment,at least one of the processor(s) 704 may be integrated on the same diewith logic for one or more controller(s) of system control logic 708.For one embodiment, at least one of the processor(s) 704 may beintegrated on the same die with logic for one or more controller(s) ofsystem control logic 708 to form a System on Chip (SoC). For oneembodiment, at least one of the processor(s) 704 may be packagedtogether with a memory of the NVM/storage 716 to form apackage-on-package (PoP). For example, a memory may be coupled with anapplications processor and configured as a PoP with the applicationsprocessor.

In various embodiments, the I/O devices 732 may include user interfacesdesigned to enable user interaction with the system 700, peripheralcomponent interfaces designed to enable peripheral component interactionwith the system 700, and/or sensors designed to determine environmentalconditions and/or location information related to the system 700.

In various embodiments, the user interfaces could include, but are notlimited to, a display (e.g., a liquid crystal display, a touch screendisplay, etc.), a speaker, a microphone, one or more cameras (e.g., astill camera and/or a video camera), a flashlight (e.g., a lightemitting diode flash), and a keyboard.

In various embodiments, the peripheral component interfaces may include,but are not limited to, a non-volatile memory port, a universal serialbus (USB) port, an audio jack, and a power supply interface.

In various embodiments, the sensors may include, but are not limited to,a gyro sensor, an accelerometer, a proximity sensor, an ambient lightsensor, and a positioning unit. The positioning unit may also be partof, or interact with, the network interface 720 to communicate withcomponents of a positioning network, e.g., a global positioning system(GPS) satellite.

In various embodiments, the system 700 may be a mobile computing devicesuch as, but not limited to, a laptop computing device, a tabletcomputing device, a netbook, a smartphone, etc. In various embodiments,system 700 may have more or less components, and/or differentarchitectures.

Although certain embodiments have been illustrated and described hereinfor purposes of description, a wide variety of alternate and/orequivalent embodiments or implementations calculated to achieve the samepurposes may be substituted for the embodiments shown and describedwithout departing from the scope of the present disclosure. Thisapplication is intended to cover any adaptations or variations of theembodiments discussed herein. Therefore, it is manifestly intended thatembodiments described herein be limited only by the claims and theequivalents thereof

What is claimed is:
 1. One or more non-transitory machine-readablestorage media, having instructions stored thereon that, when executed byone or more processors, cause a user equipment (UE) to: detect a valuein a physical downlink shared channel (PDSCH) resource element (RE)mapping field of a message received from an evolved Node B (eNB);identify, based on the value, a PDSCH RE mapping parameter set from aplurality of PDSCH RE mapping parameter sets, wherein the PDSCH REmapping parameter set includes a number of antenna ports; and processthe PDSCH RE mapping parameter set to receive a PDSCH.
 2. The one ormore non-transitory machine-readable storage media of claim 1, whereinthe number of antenna ports includes 1, 2 or
 4. 3. The one or morenon-transitory machine-readable storage media of claim 1, wherein thePDSCH RE mapping field is formed in a downlink control information (DCI)format, and is to support a coordinated multipoint (CoMP) communicationto the UE.
 4. The one or more non-transitory machine-readable storagemedia of claim 1, wherein the PDSCH RE mapping parameter set is furtherto include a frequency shift for a serving cell, a PDSCH startingsymbol, or a multicast-broadcast single frequency network subframeconfiguration.
 5. The one or more non-transitory machine-readablestorage media of claim 1, wherein the message is further to indicate aserving cell that the UE uses to receive the PDSCH.
 6. The one or morenon-transitory machine-readable storage media of claim 1, wherein theplurality of PDSCH RE mapping parameter sets have four PDSCH RE mappingparameter sets.
 7. An apparatus to be employed by a user equipment (UE),comprising: a communication module to receive, from an evolved Node B(eNB), a message having a value in a physical downlink shared channel(PDSCH) resource element (RE) mapping field; and a management modulecoupled to the communication module, the management module to: identify,based on the value, a PDSCH RE mapping parameter set from four PDSCH REmapping parameter sets, wherein the PDSCH RE mapping parameter setincludes a number of antenna ports; and process the PDSCH RE mappingparameter set to receive a PDSCH.
 8. The apparatus of claim 7, whereinthe number of antenna ports includes 1, 2 or
 4. 9. The apparatus ofclaim 7, wherein the PDSCH RE mapping field is formed in a downlinkcontrol information (DCI) format, and is to support a coordinatedmultipoint (CoMP) communication to the UE.
 10. The apparatus of claim 7,wherein the PDSCH RE mapping parameter set is further to include afrequency shift for a serving cell, a PDSCH starting symbol, or amulticast-broadcast single frequency network subframe configuration. 11.The apparatus of claim 7, wherein the message is further to indicate aserving cell that the UE uses to receive the PDSCH.
 12. An apparatus tobe employed by an evolved Node B (eNB), the apparatus comprising: amanagement module to: determine four physical downlink shared channel(PDSCH) resource element (RE) mapping parameter sets, each PDSCH REmapping parameter set having a number of antenna ports; and determine avalue in a PDSCH RE mapping field, the value corresponding to a PDSCH REmapping parameter set of the four PDSCH RE mapping parameter sets; and acommunication module coupled to the management module, the communicationmodule to transmit a message including the value in the PDSCH RE mappingfield to a user equipment (UE) over a wireless communication network.13. The apparatus of claim 12, wherein the number of antenna portsincludes 1, 2 or
 4. 14. The apparatus of claim 12, wherein the PDSCH REmapping field is formed in a downlink control information (DCI) format,and is to support a coordinated multipoint (CoMP) communication to theUE.
 15. The apparatus of claim 12, wherein the PDSCH RE mappingparameter set is further to have a frequency shift for a serving cell, aPDSCH starting symbol, or a multicast-broadcast single frequency networksubframe configuration.
 16. The apparatus of claim 12, wherein themessage is further to indicate a serving cell that the UE uses toreceive the PDSCH.
 17. The apparatus of claim 12, wherein thecommunication logic is further to transmit the four PDSCH RE mappingparameter sets to the UE.
 18. An apparatus to be employed by a userequipment (UE), the apparatus comprising: a communication module toreceive, from an evolved Node B (eNB), a message having a downlinkcontrol information (DCI) format to support coordinated multipoint(CoMP) communications, the message including a value in a channel stateinformation (CSI) request field; and a feedback module coupled to thecommunication logic, the feedback module to generate an aperiodic CSIfeedback for one or more CSI processes identified by the value in theCSI request field, wherein the one or more CSI processes are associatedwith one serving cell, and are a subset of a total number of CSIprocesses of the serving cell.
 19. The apparatus of claim 18, whereinthe value is a two-bit value that identifies the one or more CSIprocesses, wherein the one or more CSI processes are associated with theserving cell on which the message is received.
 20. The apparatus ofclaim 18, wherein the value is a two-bit value that identifies the oneor more CSI processes, wherein the one or more CSI processes areassociated with the serving cell that is different from another servingcell on which the message is received.
 21. The apparatus of claim 18,wherein the communication module is further to receive another messagein the DCI format, the other message to have a CSI request field with atwo-bit value that represents no aperiodic CSI report is triggered. 22.The apparatus of claim 18, wherein the feedback module is further toconfigure the one or more CSI processes based on a bitmap received fromthe eNB, wherein: the bitmap comprises multiple groups of bits;individual groups of the multiple groups correspond to individualconfigured serving cells including the serving cell; and individual bitsof a group correspond to individual CSI processes of a configuredserving cell that corresponds to the group.
 23. The apparatus of claim18, wherein the aperiodic CSI feedback includes a channel qualityindicator (CQI), a precoding matrix indicator (PMI), a precoding typeindicator, or a rank indicator (RI).
 24. The apparatus of claim 18,wherein individual CSI processes are associated with a CSI referencesignal (CSI-RS) resource and a CSI-interference measurement (CSI-IM)resource.
 25. The apparatus of claim 18, wherein the user equipment is amobile device having a touchscreen user interface.
 26. A method employedby an evolved Node B (eNB), comprising: generating a message having adownlink control information (DCI) format supporting coordinatedmultipoint (CoMP) communications, the message including a value in achannel state information (CSI) request field; transmitting the messageto a user equipment (UE) over a wireless communication network; andreceiving an aperiodic CSI feedback for one or more CSI processesidentified by the value in the CSI request field; wherein the one ormore CSI processes are associated with one serving cell, and are asubset of a total number of CSI processes of the serving cell.
 27. Themethod of claim 26, wherein the value is a two-bit value that identifiesthe one or more CSI processes, wherein the one or more CSI processes areassociated with the serving cell on which the message is received. 28.The method of claim 26, wherein the value is a two-bit value thatidentifies the one or more CSI processes, wherein the one or more CSIprocesses are associated with the serving cell that is different thananother serving cell on which the message is received.
 29. The method ofclaim 26, further comprising: transmitting another message in the DCIformat to the UE, wherein the other message has a CSI request field witha two-bit value that represents no aperiodic CSI report is triggered.30. The method of claim 26, further comprising: generating a bitmapcomprising multiple groups of bits, wherein individual groups of themultiple groups correspond to individual configured serving cellsincluding the serving cell, and individual bits of a group correspondingto individual CSI processes of a configured serving cell thatcorresponds to the group; and transmitting the bitmap to the UE.
 31. Themethod of claim 26, wherein the aperiodic CSI feedback includes achannel quality indicator (CQI), a precoding matrix indicator (PMI), aprecoding type indicator, or a rank indicator (RI).